| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.5.4.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.5.4 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_5_4_Clinical_Task_Status_Tracking |
| Title | AS.5.4 Clinical Task Status Tracking (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Track tasks to facilitate monitoring for timely and appropriate completion of each task. |
| Purpose | In order to reduce the risk of errors during the care process due to missed tasks, the provider is able to view the status of each task (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved) and current work lists, lists of unassigned tasks or undisposed tasks, or of other tasks where a risk of omission exists. The timeliness of certain tasks can be tracked, or reports generated, in accordance with relevant law and accreditation standards. For example, a provider is able to create a report that shows tests that have not yet been performed such as urine specimen obtained, blood work drawn, etc. Another example is that of an electronic prescribing system that would track when a refill request or prescription change is received, who it has been assigned to, the action performed, and when it was completed. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Track tasks to facilitate monitoring for timely and appropriate completion of each task.
In order to reduce the risk of errors during the care process due to missed tasks, the provider is able to view the status of each task (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved) and current work lists, lists of unassigned tasks or undisposed tasks, or of other tasks where a risk of omission exists. The timeliness of certain tasks can be tracked, or reports generated, in accordance with relevant law and accreditation standards. For example, a provider is able to create a report that shows tests that have not yet been performed such as urine specimen obtained, blood work drawn, etc. Another example is that of an electronic prescribing system that would track when a refill request or prescription change is received, who it has been assigned to, the action performed, and when it was completed.
| AS.5.4#01 | SHALL |
The system SHALL provide the ability to update the status of tasks. |
| AS.5.4#02 | dependent SHOULD |
The system SHOULD provide the ability to determine and update the status of tasks based on workflow and clinical rules and according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.5.4#03 | SHALL |
The system SHALL provide the ability to render notices of the status of tasks to providers. |
| AS.5.4#04 | MAY |
The system MAY provide the ability to capture subscription preferences for notices of changes in the status of tasks. |
| AS.5.4#05 | SHALL |
The system SHALL provide the ability to determine the order of clinical tasks based on status. |
| AS.5.4#06 | SHOULD |
The system SHOULD provide the ability to present current clinical tasks as work lists. |
| AS.5.4#07 | SHOULD |
The system SHOULD provide the ability to enter configuration parameters for filtering and rendering of clinical task lists. |
| AS.5.4#08 | SHOULD |
The system SHOULD provide the ability to render clinical task lists based on configuration entered by the user. |
| AS.5.4#09 | MAY |
The system MAY render a notification to the tasking or requesting provider when clinical tasks are complete. |
| AS.5.4#10 | SHOULD |
The system SHOULD provide the ability to enter time limits on particular tasks that have a deadline or require follow-up. |
| AS.5.4#11 | SHOULD |
The system SHOULD provide the ability to determine when time limits for particular tasks are exceeded. |
| AS.5.4#12 | conditional SHALL |
IF the system provides the ability to determine when time limits for a particular task are exceeded;, THEN the system SHALL provide the ability to render a list of these tasks. |
| AS.5.4#13 | SHOULD |
The system SHOULD render a list of tasks that have not been completed at any time including the time of patient disposition. |
| AS.5.4#14 | SHALL |
The system SHALL provide the ability to update task status (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved). |
| AS.5.4#15 | SHOULD |
The system SHOULD determine and update the status of tasks based on workflow rules. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.5.4",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Track tasks to facilitate monitoring for timely and appropriate completion of each task.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>In order to reduce the risk of errors during the care process due to missed tasks, the provider is able to view the status of each task (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved) and current work lists, lists of unassigned tasks or undisposed tasks, or of other tasks where a risk of omission exists. The timeliness of certain tasks can be tracked, or reports generated, in accordance with relevant law and accreditation standards. For example, a provider is able to create a report that shows tests that have not yet been performed such as urine specimen obtained, blood work drawn, etc. Another example is that of an electronic prescribing system that would track when a refill request or prescription change is received, who it has been assigned to, the action performed, and when it was completed.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to update the status of tasks.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine and update the status of tasks based on workflow and clinical rules and according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render notices of the status of tasks to providers.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture subscription preferences for notices of changes in the status of tasks.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to determine the order of clinical tasks based on status.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present current clinical tasks as work lists.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to enter configuration parameters for filtering and rendering of clinical task lists.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render clinical task lists based on configuration entered by the user.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY render a notification to the tasking or requesting provider when clinical tasks are complete.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to enter time limits on particular tasks that have a deadline or require follow-up.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine when time limits for particular tasks are exceeded.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system provides the ability to determine when time limits for a particular task are exceeded;, THEN the system SHALL provide the ability to render a list of these tasks.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render a list of tasks that have not been completed at any time including the time of patient disposition.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to update task status (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.4#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine and update the status of tasks based on workflow rules.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.5.4",
"version" : "2.1.0",
"name" : "AS_5_4_Clinical_Task_Status_Tracking",
"title" : "AS.5.4 Clinical Task Status Tracking (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Track tasks to facilitate monitoring for timely and appropriate completion of each task.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "In order to reduce the risk of errors during the care process due to missed tasks, the provider is able to view the status of each task (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved) and current work lists, lists of unassigned tasks or undisposed tasks, or of other tasks where a risk of omission exists. The timeliness of certain tasks can be tracked, or reports generated, in accordance with relevant law and accreditation standards. For example, a provider is able to create a report that shows tests that have not yet been performed such as urine specimen obtained, blood work drawn, etc. Another example is that of an electronic prescribing system that would track when a refill request or prescription change is received, who it has been assigned to, the action performed, and when it was completed.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-01",
"label" : "AS.5.4#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to update the status of tasks.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.3#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.4-02",
"label" : "AS.5.4#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine and update the status of tasks based on workflow and clinical rules and according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-03",
"label" : "AS.5.4#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render notices of the status of tasks to providers.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.3#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-04",
"label" : "AS.5.4#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture subscription preferences for notices of changes in the status of tasks."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-05",
"label" : "AS.5.4#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to determine the order of clinical tasks based on status.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.3#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-06",
"label" : "AS.5.4#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present current clinical tasks as work lists.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.3#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-07",
"label" : "AS.5.4#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to enter configuration parameters for filtering and rendering of clinical task lists.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.3#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-08",
"label" : "AS.5.4#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render clinical task lists based on configuration entered by the user."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-09",
"label" : "AS.5.4#09",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY render a notification to the tasking or requesting provider when clinical tasks are complete."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-10",
"label" : "AS.5.4#10",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to enter time limits on particular tasks that have a deadline or require follow-up."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-11",
"label" : "AS.5.4#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine when time limits for particular tasks are exceeded."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-12",
"label" : "AS.5.4#12",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF the system provides the ability to determine when time limits for a particular task are exceeded;, THEN the system SHALL provide the ability to render a list of these tasks."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-13",
"label" : "AS.5.4#13",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render a list of tasks that have not been completed at any time including the time of patient disposition."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-14",
"label" : "AS.5.4#14",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to update task status (e.g., unassigned, on hold, started, performed, canceled, denied, and resolved).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.4-15",
"label" : "AS.5.4#15",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine and update the status of tasks based on workflow rules.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#4"
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.